Merge VCF records at the same position together after bcftools norm left shifts them #1536
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds @Han-Cao's merge_duplicates.py as a post-processing step after
bcftools norm -f
.It merges together records at the same position that
bcftools norm
can create (see the original issue, #1493, for details).Unfortunately, it seems like
bcftools norm
can shift together sites that can't be represented as one without allele conflicts. So the--keep first
heuristic is used by default to choose one, but can be toggled in themergeDuplicatesOptions
field on the config XML.As it stands
bcftools norm -f
andmerge_duplicates.py
are both on by default forvcfwave
output. To apply it to the "Default" vcfs, thenbcftoolsNorm="1"
needs to be activated in the config.Stacks on #1491